You should ❌NOT use any process model for the purpose of modeling business decisions. Period.
This feels like an ongoing fight 🤜 Decision vs Process. I get asked this question not using a process mapping to model business decisions a lot. Almost in every conversation we have it comes up.
For us at FlexRule, it is very easy. I can say use whatever you want; we support both of them. But I'm very religious about this topic.
✨Decision models are about “what” and “why”. A process model is about “how” (and sometimes “when”).
This may sound like a trivial difference, but it is the difference between success and failure. Sure, you can model a decision using process mapping or BPMN etc. You can also model business processes using Java or Python code on any #lowcode #nocode app development platform. But because you can, it does not mean you should.
The challenge is to make sure we strictly stay on and focus on the purpose of the modeling of decision: separation of “what” and “why” from “how”.
💥In process mapping/modeling, because of all the options you have at your disposal, you very quickly and simply deviate from this purpose without even noticing it.
💣Very significant values of decision modeling are derived from the separation of concern: “what” and “why” from “how”:
* Clarity in communication
* Absolute transparency on making business decisions
* Ease of understanding without too much details
* Flexibility in “how” a decision is satisfied
* Decomposition opportunity to make a complex decision to simpler decision units
🚀 To ensure “what” and “why” are not easily mixed with “how,” based on the first principle of separation of concerns. Therefore, you SHOULD use decision modeling for business decisions, not a process mapping or modeling approach.
#insurance #government #banking #decisionintelligence
Posted here.
Published July 26th, 2024 at 07:30 am
